I understand.  The forcefulness and persuasiveness of the requests we get from users is a factor in deciding what we're going to do next.  As you can see from my response yesterday, Gangee, you've already forced me to think through what needs to be done.

Gangee, now that I understand how you're using BookMacster, I think I know why the Bark Hack is not working for you.  Broadly, there are three ways to use BookMacster.  You're doing what we call Usage Style 1, or maybe Usage Style 2, which means that you're syncing with browser(s).  Another group of BookMacster users does what we call Usage Style 3, which means that they never use the built-in bookmarks in their web browsers and instead add bookmarks to BookMacster and visit bookmarks from BookMacster directly, using one of it widgets, bookmarklet, status menulet, dock menu and/or keyboard shortcut.

The Bark Hack replaces the built-in Page Rip sound which BookMacster can make when adding a bookmark directly (Usage Style 3) with a Bark.  I think what you want is to have a sound effect when BookMacster exports to a Client.  This is what Bookdog did.

If I am correct, then you can't have that until we add that feature to BookMacster.  That's possible, now that it looks like we've got this iCloud thing behind us.  But it's got to be considered along with a large pile of other feature requests.

We found a bug or two which caused Agent operations to not trigger automatically for Gangee.  The fix will be in BookMacster version 1.9.3, which we'll probably publish in a few days, probably on the Beta channel.

The problem is that BookMacster's Worker is choking on a garbage file that got stranded after some extraordinary event.  If anyone with this issue really wants a workaround to fix it now, here it is:

• Launch BookMacster.
• Open your Bookmarkshelf with the agent(s) if it does not open.
• Click to the tab Settings ▸ Agents.
• If you're in Simple, switch all the boxes OFF, then switch the ones which were ON back ON.  If you're in Advanced, do the same thing to the Active boxes in the (top) Agents table.
• Navigate in Finder to your home's LaunchAgents, that is,
    ~/Library/LaunchAgents/
• See if you have any files whose name begins with "com.sheepsystems.BookMacster" and has "doSoon" or "doOver" near the end.  For example,
    com.sheepsystems.BookMacster.4299B333-C47D
       -4473-B329-41F43E22E886.000.000.doOver.02523.plist
• If you don't have any such files, the issue may have fixed itself, or it's a different issue.
• If you do have any such files, delete or trash them.

Triggering should start working again after the next time you log out and back in.  Instead of logging out and in, if you know how to use launchctl you can unload the agent(s) whose files were just deleted.

paul@eagleranch.co wrote on Dec 6^th, 2011 at 8:36pm:

That may be a clue.  Are you working from an Administrator account…

• Click in the menu  ▸ System Preferences.
• Click Users & Groups.
• Is the box "Allow user to administer this computer" switched ON?

I see.  Indeed the sort that took place 2 hours later, at 9:47, but it was because you launched BookMacster manually, your Bookmarkshelf opened, and this Bookmarkshelf is set to import, sort and export upon opening.  That is, it finally happened due to your manual intervention.  That's cheating and doesn't count.

In your logs, I see that the Worker process whose ID (PID) is 3242 was invoked this morning at 7:33:40, announced that it was caused by Safari bookmarks being touched, and then disappeared.  When I look through my logs, such a process always logs two more entries: either "Staging job to run at XX:XX" (5 minutes later) or "Job already staged", followed by "Exitting with status 0 (No error)".  PID 3242 should have done this, staging a job to run at 7:38, and the fact that it did not is why sorting did not occur as expected.  I see two other similar PIDs in your log with the same premature terminations, so it was not a fluke and not a system crash.

For some reason, these little staging jobs are getting terminated before they do their staging on your Mac, and that's why your automatic sorts are not working.

Please activate BookMacster, click in the menu Help ▸ Trouble Zipper, and click through it.  If you wouldn't mind Trouble Zipper sending me your data, maybe I could reproduce these premature terminations.

Thanks, Gangee.

paul@eagleranch.co wrote on Dec 6^th, 2011 at 4:21pm:

The first two most recent entries in that log (at 7:33:40) indicate that the change to Safari bookmarks was detected, and that Mac OS X launched BookMacster-Worker to do something about it.  So far, so good.

In order to reduce system loading, these logs don't refresh automatically from other processes (that is, we don't use Distributed Notifications).  Click the round "refresh" button in the upper left corner, and we'll probably see more.

paul@eagleranch.co wrote on Dec 6^th, 2011 at 4:21pm:

Either post another screenshot after the refresh, or send me the file…
    ~/Library/Application Support/BookMacster/Logs.sql
whichever you like.

paul@eagleranch.co wrote on Dec 6^th, 2011 at 4:21pm:

It would be a handy troubleshooting tool for this, but I don't want to troubleshoot two things at once.  Let's just use the logs for now.

Was 7:33 about the time that you added the bookmark which has not yet been sorted?

Good morning Jerry,

OK. I added two bookmarks over an hour ago, they're added but not sorted.

So now what? I checked the logs, nothing seems to be in there to indicate a sort.

Do I need to email you the log?

Also, I'm not getting any sounds -- at all. I put the bark file in the folder you said to, it's there. No sounds at all now.

= gangee